Hi @tom-schier,

Thank you for raising this PR.

To help us review and confirm the changes required for the authorisation-server, we need information regarding why the changes are required and why the current offering does not provide what is needed. Please use the feature request template to provide more details and link the feature to the Pull Request.

Some of the questions we have are:

• What use case(s) does hosting the authorisation-server gateways outside of the existing docker container support?
• How would a user run the authorisation-server docker container whilst also utilising the gateway docker containers?
• What behaviour is experienced when using the new gateway docker containers with the existing authorisation-server docker container?
• How can testing of the gateway docker containers be automated so they are not impacted by a future release and maintenance overheads are reduced?

Once we get through the requirements and feature confirmation, there will be a couple of additions needed:

• Creation of automated tests
• Update added to the changelog
• Depending on how the feature works, documentation changes will most likely be required

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

Hi @tom-schier

TLS and MTLS gateways are tightly coupled with the authorisation-server and serve routing to the authorisation-server on specific hostnames and ports in a local development environment.

Moving TLS and MTLS gateways out into their own container images might not benefit the community. Additionally, it will require the community to design and configure their auth server implementation in a specific way that aligns with these TLS and MTLS gateways.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.